Network system, control apparatus, method for constructing a virtual network, and program

ABSTRACT

A network system is connected to a first physical network comprising: a first data transmission node that transmits data used for a first service and a second data transmission node that transmits data used for a second service and to a second physical network including at least one apparatus for receiving data from the first and the second data transmission nodes, and constructs a virtual network for each service between the first and the second physical networks.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a Continuation application of Ser. No.16/077,106 filed on Aug. 10, 2018, which is a National Stage ofInternational Application No. PCT/JP2017/008144 filed Mar. 1, 2017, andis based upon Japanese patent application No. 2016-040429 filed on Mar.2, 2016, the disclosure of which is incorporated herein in its entiretyby reference thereto.

FIELD

The present invention relates to a network system, control apparatus,method for constructing a virtual network, and program, and inparticular relates to a network system, control apparatus, method forconstructing a virtual network, and program that treat data acquiredfrom a sensor.

BACKGROUND

Patent Literature 1 discloses an inter-LAN (Local Area Network)connection service operation coordination apparatus in which a user of aconnection service between LANs enables configuration change of anetwork portion of a connection service managed by a telecommunicationscarrier. According to this publication, the inter-LAN connection serviceoperation coordination apparatus enables setting of a connected networkand information collection from a LAN side, in a serviceinter-connecting a plurality of user LANs using a connected network.There is a description that the inter-LAN connection service operationcoordination apparatus has an agent that defines a connected network asa virtual switch or router using user-available resources for each user,possible settings, and information that can be referred to; that retainsthe definition information; and that enables control of the virtualswitch or router from the LAN side; and the agent has a means to performprocessing when a command is received from the LAN side, in response tothe command, on a apparatus in the connected network.

Patent Literature 2 proposes a new platform that preferably integratesnetwork virtualization technology and cognitive wireless technology.According to this literature, the cognitive virtualization networksystem uses a wired core network connected to a plurality of physicalwireless access networks, and configures a core network formed of atleast one of: the wired core network itself or a virtual core networkconfigured virtually in the wired core network; and also configures avirtual cognitive wireless base station corresponding to a single oreach of a plurality of the core networks at respective physical basestations of the wireless access network; and by establishingcommunication with the virtual cognitive wireless base station, acognitive communication terminal can connect to the cognitivevirtualization network formed from the core network and the virtualcognitive wireless base station. The cognitive virtualization networksystem is characterized in that it is possible to dynamically rebuildthe single or plurality of cognitive virtualization networks that formthe cognitive virtualization network system.

Patent Literature 3, in a configuration in which Ethernet (registeredtrademark) LANs, LAN1, LAN2, and LAN3, are each connected to an IP(Internet Protocol) network N by respective client edge apparatuses CE1,CE2, CE3, discloses a configuration in which exchange of controlinformation associated with Ethernet packet transmission between theclient edge apparatuses CE1, CE2 and CE3 is processed and controlled byan integrated server 10 connected to the respective client edgeapparatuses CE1, CE2, CE3 via a control connection 21.

Patent Literature 4 discloses an access control system that enablescontrol, in a case of inter-connecting home LANs by VPN (Virtual PrivateNetwork), of access to content retained in information domesticappliances connected by a home LAN.

Patent Literature 5 discloses an information collection system in whichit is possible to report the occurrence of an abnormality with highaccuracy, even where a concrete pole supporting electrical wiringcollapses. Specifically, the information collection system has aninclination detection sensor that detects a change in statecorresponding to the inclination of the concrete pole, and a wirelesscommunication part that transmits detection information of theinclination detection sensor and self-identification information; andthe system is provided with a sensor node attached to the concrete pole,and a gateway server that collects transmission information transmittedfrom the sensor node, and transmits the collected information to anothercommunication network with a different communication protocol from thesensor node. With regard to the abovementioned sensor node, a wirelessad-hoc network is mutually configured with a sensor node installed inanother concrete pole existing within a communicable distance.

Patent Literature 6 discloses a configuration in which meter readingdata is collected at low cost, in a short time, and with highreliability, in a system in which multiple meter terminals transmitmeter data to a host apparatus by multi hop wireless communication.

Patent Literature 7 discloses a VPN connection system in which VPNconnectivity is assuredly enabled to terminals, by suitably generatingrouting information between a VPN connection destination network andterminals using VPN in a virtual environment.

Non-Patent Literature 1 is a white paper on Network FunctionsVirtualization (NFV) related to an exemplary embodiment of the presentinvention.

CITATION LIST Patent Literature (PTL)

[Patent Literature 1]

Japanese Patent Kokai Publication No. JP2002-9847A

[Patent Literature 2]

Japanese Patent Kokai Publication No. JP2012-49712A

[Patent Literature 3]

Japanese Translation of PCT International Publication, Publication No.2014-523173 A

[Patent Literature 4]

Japanese Patent Kokai Publication No. JP2009-188622A

[Patent Literature 5]

Japanese Patent Kokai Publication No. JP2006-217704A

[Patent Literature 6]

Japanese Patent Kokai Publication No. JP2011-34388A

[Patent Literature 7]

Japanese Patent Kokai Publication No. JP2013-21423A

Non Patent Literature(NPL)

[Non-Patent Literature 1]

European Telecommunications Standards Institute (ETSI), “NetworkFunctions Virtualization—Update White Paper”, [online], [retrieved onJan. 20, 2016],

Internet <URL:https://portal.etsi.org/NFV/NFV White Paper2.pdf>

SUMMARY

The following analysis is given according to the present invention. Asin Patent Literature 5 and 6, technology used in various forms isbecoming widespread, whereby sensor nodes or meter terminals are given acommunication function, carry out mutual communication, and collectdata. In this type of technology, “things” are said to be connected tothe Internet, so the term “Internet of Things” (IoT) is used.

Exemplary embodiments of IoT network systems include IoT apparatusesconnecting to the internet via edge nodes such as gateways (GW) or thelike, and individual IoT apparatuses connecting directly to the Internetor cloud, and if consideration is given to power consumption in the IoTdevices, the former is advantageous. It is to be noted that both PatentLiterature 5 and 6 employ the former in which gateways are disposed.

Henceforth, in IoT network systems, it is expected that monitoring andcontrol will be carried out by sensors or the like, deployed bydifferent carriers at the same site (for example, factory, office, home,street or the like). However, since carriers A and B are in acompetitive relationship in different industries or the same industry,there is a demand to separate the networks. Since most of the datacollected by these sensors relate to data for which there is a duty ofconfidentiality, such as personal information, company secrets, or thelike, from this viewpoint also a need arises for isolating networks.

In such cases, each carrier separately prepares edge nodes with theirrespective responsibilities, and there is a problem regarding thenecessity to isolate the networks. In actuality, in a case where aplurality of edge nodes are deployed, a problem occurs with regard toinstallation space in a home or the like, and a problem of cost arisesin offices with regard to security management thereof, and disposing andmanagement of these edge nodes.

It is an object of the present invention to provide a network system, acontrol apparatus, and a method and program for building a virtualnetwork function, which can contribute to solving various problemsrelated to a network in which a plurality of data transmission entitiesare deployed to transmit data used in different services.

According to a first aspect, a network system is provided that connectsto a first physical network comprising: a first data transmission nodethat transmits data used for a first service and a second datatransmission node that transmits data used for a second service; and asecond physical network including at least one apparatus for receivingdata from the first and the second data transmission nodes. Moreconcretely, the network system constructs a virtual network between thefirst and the second physical networks for each of the services.

According to a second aspect, there is provided a control apparatusconnected to a first edge node provided on a boundary with a firstphysical network comprising: a first data transmission node thattransmits data used for a first service and a second data transmissionnode that transmits data used for a second service and to a second edgenode provided on a boundary with a second physical network including atleast one apparatus for receiving data from the first and the seconddata transmission nodes; and the control apparatus comprises means forcontrolling the first and the second edge nodes and constructing avirtual network for each of the services between the first and thesecond physical networks.

According to a third aspect, there is provided a method for constructinga virtual network comprising: causing a control apparatus, which isconnected to a first edge node provided on a boundary with a firstphysical network including a first data transmission node that transmitsdata used for a first service and a second data transmission node thattransmits data used for a second service and to a second edge nodeprovided on a boundary with a second physical network including at leastone apparatus, to receive data from the first and the second datatransmission nodes receive setting information for constructing avirtual network for each of the services between the first and thesecond physical networks; and

causing the control apparatus to control the first and the second edgenodes and to construct a virtual network for each of the services on thebasis of the setting information. The present method is tied to aparticular machine, namely, the control apparatus that controls the edgenodes.

According to a fourth aspect, there is provided a program having acomputer connected to a first edge node provided on a boundary with afirst physical network comprising: a first data transmission node thattransmits data used for a first service and a second data transmissionnode that transmits data used for a second service and to a second edgenode provided on a boundary with a second physical network including atleast one apparatus for receiving data from the first and the seconddata transmission nodes execute a process of receiving settinginformation for constructing a virtual network for each of the servicesbetween the first and the second physical networks; and a process ofcontrolling the first and the second edge nodes and constructing avirtual network for each of the services on the basis of the settinginformation. Further, this program can be stored in a computer-readable(non-transient) storage medium. In other words, the present inventioncan be realized as a computer program product.

The meritorious effects of the present invention are summarized asfollows.

According to the present invention, management is facilitated for dataflowing in a network in which a plurality of data transmission entitiesare deployed to transmit data used by different services. Namely, thepresent invention can transform a network system into a network systemthat is more facilitated for management of data flowing in a network.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram showing a configuration of an exemplary embodimentof the present disclosure.

FIG. 2 is a diagram showing an application example of an exemplaryembodiment of the present disclosure.

FIG. 3 is a diagram showing a configuration of a network system in afirst exemplary embodiment of the present disclosure.

FIG. 4 is a functional block diagram showing a detailed configuration ofa controller in the first exemplary embodiment of the disclosure.

FIG. 5 is a diagram showing an example of authentication informationheld by the controller in the first exemplary embodiment of thedisclosure.

FIG. 6 is a diagram showing an example of virtual network settinginformation held by the controller in the first exemplary embodiment ofthe disclosure.

FIG. 7 is a sequence diagram representing operations of the networksystem in the first exemplary embodiment of the disclosure.

FIG. 8 is a diagram for describing operations of the network system inthe first exemplary embodiment of the disclosure.

FIG. 9 is a diagram showing a configuration of a network system in asecond exemplary embodiment of the present disclosure.

FIG. 10 is a diagram for describing the concept of an NFV used in thesecond exemplary embodiment of the disclosure.

FIG. 11 is a diagram for describing a data plane configuration of theVNF in the second exemplary embodiment of the disclosure.

FIG. 12 is a diagram for describing a control plane configuration of theVNF in the second exemplary embodiment of the disclosure.

FIG. 13 is a diagram for describing an example of a configuration methodfor an IoT-GW in the network system in the second exemplary embodimentof the disclosure.

FIG. 14 is a diagram for describing another example of a configurationmethod for an IoT-GW in the network system in the second exemplaryembodiment of the disclosure.

FIG. 15 is a diagram for describing a configuration of an IoT-GW in thenetwork system in a third exemplary embodiment of the disclosure.

FIG. 16 is a diagram for describing another example of a configurationmethod for an IoT-GW in the network system in the third exemplaryembodiment of the disclosure.

FIG. 17 is a diagram showing a configuration of a network system in afourth exemplary embodiment of the disclosure.

FIG. 18 is a diagram for describing operations of a network system inthe fourth exemplary embodiment of the disclosure.

FIG. 19 is a diagram for describing a modified example of the fourthexemplary embodiment of the disclosure.

FIG. 20 is a diagram for describing another modified example of thefourth exemplary embodiment of the disclosure.

FIG. 21 is a diagram showing a configuration of a network system in afifth exemplary embodiment of the disclosure.

PREFERRED MODES

First, a description is given of an outline of exemplary embodiments ofthe present invention, making reference to the drawings. It is to benoted that reference symbols in the drawings attached to this outlineare added to respective elements for convenience, as examples in orderto aid understanding, and are not intended to limit the presentinvention to modes illustrated in the drawings. Connection lines betweenblocks in the drawings used in the following description may beunidirectional or bidirectional. Unidirectional arrows schematicallyshow flow of main signals (data), but do not exclude bidirectionality.In addition, although there are ports or interfaces at the connectionpoints of the input and output of each block in the figures, they areomitted.

An exemplary embodiment of the present disclosure may be realized asshown in FIG. 1, by a network system 400, deployed between a firstphysical network 100 and a second physical network 200, the systemconfiguring virtual network functions according to service.

More specifically, the first physical network 100 includes a first datatransmission node (for example, sensor A in FIG. 1) that transmits dataused in a first service, and a second data transmission node (forexample, sensor B in FIG. 1) that transmits data used in a secondservice.

Meanwhile, the second physical network 200 includes apparatuses (serviceA apparatus and service B apparatus in FIG. 1) for receiving data fromthe first and second data transmission nodes. The network system 400configures virtual network functions for each respective service betweenthe 2 networks (refer to arrows between edge nodes 310 and 320 in FIG.1). Thus, it is possible to transmit data obtained by respective datatransmission nodes, with different networks.

It is to be noted that various methods may be considered with regard tomethods of configuration of the virtual network functions. For example,as shown in FIG. 1, it is possible to realize tunneling corresponding toa virtual network between the edge node 310 deployed at an edge of thefirst physical network 100 and the edge node 320 deployed at an edge ofthe second physical network 200.

When the tunneling is performed, data transmitted from the firstphysical network 100 is, for example, encapsulated by the edge node 310,and transmitted to the second physical network 200. Data transmitted tothe second physical network 200 is, for example, encapsulated by theedge node 320, and is transmitted to the service A apparatus or theservice B device.

As another technique it is possible to provide a controller to controlthe network between the first physical network 100 and the secondphysical network 200, and to employ a method of logically slicing thenetwork.

In this case, the controller respectively generates a data forwardingpath for transmitting data of sensor A and a data forwarding path fortransmitting data of sensor B. Notification is given of a processingrule for data transmission so as to transmit respective data by thegenerated forwarding path to each data forwarding apparatus (not shownin the drawings) included in the network system 400.

FIG. 2 is a diagram showing a specific application example of theconfiguration of FIG. 1. FIG. 2 shows a configuration in which aphysical network 101 and a data center 201 are connected via the networksystem 400. The physical network 101 includes a carrier A terminal and acarrier B terminal (equivalent to the abovementioned “data transmissionnodes”) to which a plurality of sensor groups including sensors 600 aand sensors 600 b are connected (described below as “sensor 600” wheresensors 600 a and sensors 600 b are not particularly distinguished), andan IoT-GW 311.

Sensor 600 a is a sensor installed by carrier A, sensor 600 b is asensor installed by carrier B, and they are respectively connected tothe carrier A terminal and the carrier B terminal. The carrier Aterminal and the carrier B terminal are each connected to the IoT-GW311.

Meanwhile, the data center 201 (equivalent to the second physicalnetwork) includes a virtual network built for each respective carrier(virtual NW-A and virtual NW-B), and a GW 321. Here, the virtual NW-A isa virtual network built for carrier A, and the virtual NW-B is a virtualnetwork built for carrier B.

It is to be noted that in the description above, a virtual network isbuilt for each carrier, but it is also possible to build a virtualnetwork function for each service (here, a “service” is a function orconvenience provided directly or indirectly to a user, using datacollected by a sensor). In other words, in a case of providing aplurality of services, where the same carriers have the same base, forexample, a virtual network function may be built for each respectiveservice. Below, the description of “for a particular carrier (for eachcarrier)” may also be read as “for every service (for each service)”.

In the configuration of FIG. 2, the network system 400 builds a virtualnetwork function for each carrier, between the physical network 101 andthe data center 201 (refer to arrows between the IoT-GW 311 and the GW321 in FIG. 2). The IoT-GW 311 then transmits data received by thecarrier A terminal from sensor 600 a to the GW 321 opposite, via thevirtual network (VLAN 1) for carrier A. Similarly, the IoT-GW 311 thentransmits data received by the carrier B terminal from sensor 600 b tothe GW 321, via the virtual network (VLAN 2) for carrier B. The GW 321forwards data received via the virtual network for carrier A to thevirtual NW-A inside the data center 201, and forwards data received viathe virtual network for carrier B to the virtual NW-B inside the datacenter 201.

In a case where carrier A provides a service for managing electricalpower income/expenditure within a home, sensor data of each home(consumed power and solar power generated amount) is obtained fromsensor 600 a. Meanwhile, in a case where carrier B provides a servicefor air-conditioning control in an office, data of office thermometer orair-conditioner operating state is obtained from sensor 600 b.

According to the configuration of FIG. 2, respective carrier terminalsthat have obtained the data transmit the data received from the sensor600 to the IoT-GW 311. The IoT-GW 311 selects a transmission destinationand a network to be used for data transmission to the transmissiondestination (forwarding path), according to a setting by the networksystem 400, in accordance with a transmission source terminal of thereceived data, and sorts and transmits the data to the GW 321. The GW321 identifies a virtual network by which the data has been sent, andforwards the received data to a virtual network within the data center201. Clearly, it is also possible for the IoT-GW 311 to perform suitableprocessing such as statistical processing of received data, adjustmentof transmission frequency, or the like.

In this way, sensor data (power consumption, solar power generationamount) of each home, for example, is forwarded to the virtual NW-A ofcarrier A that provides a service using this data. Carrier A provides amanagement service for power income/expenditure or a prediction servicefor power demand/power generation for an entire area or the like, basedon sensor data (power consumption, solar power generation amount) ofeach home.

Similarly, office thermometer or air conditioner operation state data,for example, is forwarded to the virtual NW-B of carrier B that providesa service using this data. Carrier B provides an office air-conditioningmanagement service, based on the office thermometer or air conditioneroperation state data.

In this way, according to the embodiment of FIG. 2, it is possible toseparately handle data of multiple carriers. A separate carrierrequested to analyze data from carrier A or carrier B may perform bigdata analysis and provide results thereof to carriers A and B.

FIRST EXEMPLARY EMBODIMENT

Next, a detailed description is given concerning a first exemplaryembodiment of the present disclosure, making reference to the drawings.FIG. 3 is a diagram showing a configuration of a network system in thefirst exemplary embodiment of the disclosure. FIG. 3 shows aconfiguration in which a first network 101 a and a data center 201 areconnected via a third network 401.

The first network 101 a, for example, is a network configured in afactory, office or home, in which sensors 600 a and 600 b of carrier Aand carrier B are deployed. An IoT-GW 311 is deployed in the firstnetwork 101 a as an edge node, to transmit data sent from terminals ofrespective carriers to the data center 201, via the third network 401.It is to be noted that connections between the sensor 600, carriers Aand B, and the IoT-GW 311 may be wired or may be wireless.

A virtual network (virtual NW-A) of carrier A and a virtual network(virtual NW-B) of carrier B are built in the data center 201. Devicesfor respective carriers to provide services are connected to the virtualNW-A and the virtual NW-B. In the data center 201, a tunnel isestablished with the IoT-GW 311 on the first network 101 a side, and aGW 321 that performs exchange of data is deployed.

In the third network 401 the IoT-GW 311 and a controller 500 thatcontrols the GW 321 are connected.

On receiving data from the sensor via a carrier terminal, the IoT-GW 311refers to virtual network information (tunnel information) set therein,specifies a virtual network to which the sensor in question belongs,adds (encapsulates) a suitable tunnel header, and forwards to the datacenter 201. In a case where the identification number of a transmissionsource sensor for data received from a carrier terminal is unknown, thatis, the virtual network for transmission cannot be identified, theIoT-GW 311 transmits the identification number of the sensor in questionto the controller 500, and enquires whether or not data from the sensor600 should be transmitted to the data center 201, and enquires about thevirtual network in a case of transmitting the data. As a result of theenquiry, in a case of a response that the data may be transmitted to thedata center 201 side, the IoT-GW 311 transmits the received data via thevirtual network specified by the controller 500. In a case of receivingdata from the GW 321 on the data center 201 side, the IoT-GW 311 removes(decapsulates) the tunnel header added to the data, and forwards to acarrier terminal specified in the destination.

On receiving data from the IoT-GW 311, via the third network, the GW 321removes the tunnel header added to the data and forwards to the virtualNW-A or the virtual NW-B on the data center 201 side which is thedestination. In a case of receiving data to be transmitted to the firstnetwork 101 a side from the virtual NW-A or the virtual NW-B, similarlyto the IoT-GW 311, the GW 321 transmits to the IoT-GW 311, via thevirtual network specified by the controller 500.

FIG. 4 is a functional block diagram showing a detailed configuration ofthe controller in the first exemplary embodiment of the disclosure. FIG.4 shows the controller 500 provided with an authentication informationstorage part 501, a virtual network setting storage part 502, anauthentication part 503, and a virtual network control part 504.

The authentication information storage part 501 stores information fornewly authenticating a sensor, regarding which an attempt is newly madeto transmit data to the data center side, within the sensor 600. FIG. 5is a diagram showing an example of authentication information held bythe authentication information storage part 501. The example of FIG. 5shows a table associating sensor ID (sensor identification information),ID (identification information) of a virtual network to which the sensorbelongs, and user (sensor owner). It is to be noted that regarding theaddition of an entry to the authentication information storage part 501,when respective carriers newly add a sensor, the controller 500 may beaccessed and registration performed each time. Or, at a prescribedtrigger, the controller 500 may query a carrier terminal, extractinformation of a sensor that is legitimately connected, and performautomatic registration. It is to be noted that the sensor ID (sensoridentification information) may be information to enable each sensor tobe uniquely identified, and for example, it is possible to use a MACaddress (Media Access Control address) assigned to the sensor itself,apparatus ID or product serial information or the like.

The authentication part 503 uses information held in the authenticationinformation storage part 501 to implement authentication of an unknownsensor. Specifically, in a case of receiving a query as to possibilityof transmitting unknown sensor data from the IoT-GW 311, theauthentication information storage part 501 determines whether or not totransmit the data from the sensor in question, according to whether ornot the ID of the sensor in question is registered. In a case of successin authentication, in other words, a determination that it is possibleto transmit data from the sensor in question, the authentication part503 gives notification of the virtual network ID to which the sensor inquestion should belong, to the IoT-GW 311.

The virtual network setting storage part 502 holds information of atunnel established between edge nodes (GW). FIG. 6 is a diagram showingan example of virtual network setting information held by the virtualnetwork setting storage part 502. The example of FIG. 6 shows a tableassociating an address to be used as a tunnel header and a virtualnetwork ID to be assigned, for each edge node (GW).

The virtual network control part 504 refers to content registered in thevirtual network setting storage part 502, and performs setting of atunnel for the IoT-GW 311 and the GW 321. Specifically, notification isgiven to a GW shown in the GW ID field in FIG. 6, of a list of sensorsbelonging to respective virtual networks, virtual network IDs thereof,address information to be used in a tunnel header, and the like. It isto be noted that for tunneling protocols, use may be made of overlayvirtual network technology, such as NVGRE (Network Virtualization usingGeneric Routing Encapsulation), VXLAN (Virtual Extensible Local AreaNetwork), or the like. In such a case, a TNI (Tenant Network Identifier)in NVGRE or a VNI (VXLAN Network Identifier) in VXLAN may be used as theabovementioned virtual network ID.

It is to be noted that the respective parts (processing means) of thecontroller 500 shown in FIG. 4 can be implemented by a computer programthat executes the abovementioned respective processing on a computerconfiguring the controller 500, using hardware thereof.

It is to be noted that in the example of FIG. 3 the controller 500 isconnected to a third network 401, but the controller 500 arrangement isnot limited to the example of FIG. 3. For example, the controller 500may be connected to the first network 101 a or the data center 201 side.

Continuing, a detailed description is given concerning operations of thepresent exemplary embodiment, making reference to FIG. 7 and FIG. 8.FIG. 7 is a sequence diagram representing operations of the networksystem in the first exemplary embodiment of the disclosure. FIG. 7represents operations of an example in which a terminal of carrier Areceives data from a newly added sensor. Referring to FIG. 7, first, onreceiving data from the newly added sensor (step S001), the carrier Aterminal transmits the data received from the sensor to the IoT-GW 311(step S002). The data includes a sensor ID of the sensor in question.

On receiving the sensor data from the carrier A terminal, the IoT-GW 311confirms whether or not the sensor ID in question is present, in a list(refer to sensor ID field in FIG. 5) of sensors specified in virtualnetwork information pre-set by the controller 500. If it is ascertainedas a result of the confirmation that this is an unknown sensor, theIoT-GW 311 transmits the ID of the sensor in question to the controller500, and queries whether or not data from the sensor in question may besent to the data center 201, and queries the virtual network in a casewhere the data is transmitted (step S003, refer to “query” in FIG. 8).

The controller 500 that receives the query refers to the authenticationinformation storage part 501, and determines whether or not to transmitthe data from the sensor that has received the query, to the data center201 side (step S004). As a result of the determination, in a case ofdetermining that the data from the sensor that has received the querymay be transmitted to the data center 201 side, the controller 500 givesnotification to the IoT-GW 311 and the GW 321, of a virtual network IDto which the sensor that has received the query should belong (stepS005, refer to “control” in FIG. 8).

The IoT-GW 311 and the GW 321 that have received the notification addthe sensor ID notified from the controller 500, to a list of sensors invirtual network information held by each thereof (refer to sensor IDfield in FIG. 5). The IoT-GW 311 forwards the data received in stepS002, via a virtual network specified by a virtual network ID notifiedfrom the controller 500 (step S006).

Below, due to being registered in the IoT-GW 311 and the GW 321,information of a new sensor is forwarded directly to the data center201, without a query being made to the controller 500.

As described above, according to the present exemplary embodiment, it ispossible to build and use an IoT network without each carrier providingdedicated IoT-GWs. It is to be noted that in the abovementionedexemplary embodiment, in order to simply the description, there are 2carriers A and B, but there is no limit to the number of carriers.

In the present exemplary embodiment, more preferably the controller 500may provide a function to update registered content of the virtualnetwork setting storage part 502, under appropriate access limitation,with regard to carriers A and B. By so doing, it is possible to obtainan effect equivalent to carriers A and B each having a dedicated GWinstalled and a virtual network function built.

SECOND EXEMPLARY EMBODIMENT

Continuing, a detailed description is given concerning a secondexemplary embodiment of the present disclosure in which an IoT-GW isconfigured using network function virtualization (below, “NFV”), makingreference to the drawings. FIG. 9 is a diagram showing a configurationof a network system in the second exemplary embodiment of thedisclosure. A point of difference from the first exemplary embodiment isthat the IoT-GW 311 is substituted by a VNF IoT-GW 311 a configured by aVNF (Virtual Network Function). Since the basic configuration andoperations are otherwise the same as the first exemplary embodiment, thedescription below is centered on points of difference.

First a description is given of the basic concept of network functionvirtualization (below “NFV”). FIG. 10 is a diagram for describing theconcept of NFV. Reference symbol 901 in FIG. 10 represents NFVI (NetworkFunction Virtualization Infrastructure: NFVI) that forms an executioninfrastructure for VNF, and is configured by hardware resources such asswitches and servers forming operation infrastructure for VM (virtualmachines). In other words, the NFVI 901 is an infrastructure in whichhardware resources such as servers and the like are flexibly handled asvirtual hardware resources, such as virtualized computing, virtualizedstorage, and virtualized networks, virtualized in virtualized layers ofa hypervisor or the like.

Reference symbol 902 of FIG. 10 shows a virtualized network functiongroup (VNFs) realized in software called VNF (Virtual Network Function).Respective VNFs correspond to applications operating in virtual machines(VMs) on a server. In the present exemplary embodiment the VNF (IoT-GW)321 a is configured as an IoT-GW using this VNF.

A VM management part 903 in FIG. 10 manages a VM, is also called aVNF-Manager (VNFM), and performs VNF lifecycle management(instantiation, updating, search, scaling, termination, healing, and thelike) and event notification.

A NW management part 904 is a means for realizing desired servicechaining by controlling data flow between VMs operating in 1 or moreservers. FIG. 11 shows an example of service chaining configured by 2VMs (VM1, VM4) operating in 2 servers X and Y, by controlling 2switches. FIG. 12 shows a control plain for controlling the 2 switchesand servers. In the example of FIG. 12, the VM management part 903 andthe NW management part 904 are deployed in a controller 930, and inaccordance with an instruction from an operator (management terminal)906, the respective servers and switches can be controlled. It is to benoted that the controller 930 may be a apparatus similar to thecontroller 500 of FIG. 9. Below, in the present exemplary embodiment adescription is given in which the controller 500 of FIG. 9 functions asthe controller 930 of FIG. 12.

An orchestrator 905 performs orchestration of the abovementioned NFVI901 and VNFs 902, in accordance with operation control instructions forthe system inputted by an operator 906. The operator 906 is equivalentto OSS (Operation Service Systems) or BSS (Business Service Systems) ofNon-Patent Literature 1.

Continuing, a description is given concerning a method of configuringthe VNF IoT-GW 311 a in the present exemplary embodiment. FIG. 13 is adiagram for describing an example of a configuration method for anIoT-GW in the network system in the second exemplary embodiment of thepresent disclosure. For example, carrier A accesses the controller 500from an operator (management terminal) 906 deployed in a virtual NW on adata center 201 side, and transmits a request to create the VNF IoT-GW(function implementation request). The controller 500 implementsfunction implementation control so as to create the IoT-GW 311 a as aVNF as shown in FIG. 13.

According to the present exemplary embodiment, carrier A can performfunction customizing for the IoT-GW 311 a without providing its ownhardware or software. In this case, carrier A may access the controller500 from the operator (management terminal) 906, and transmit a request(function implementation request) to add or remove a function of the VNFIoT-GW 311 a. The controller 500 that has received the request changesan application operating on the VM corresponding to the VNF IoT-GW 311 aof FIG. 13, and by changing chaining between VMs, implements control toadd/remove functions. As a function to add to the VNF IoT-GW 311 a,various functions can be considered such as adding prescribed processingto data received from respective sensors (for example, statisticalprocessing of averages or aggregation), adding data held by the VNFIoT-GW 311 a to data received from respective sensors (previous dayvalue, previous month value, previous year value, or reference valuesfor data comparison).

As shown in FIG. 13, a request to create an IoT-GW (functionimplementation request) or a function change request may be sent from abusiness network (on-premises network) of carrier A, rather than fromthe data center 201 side. As shown in FIG. 14, it is possible to have anarrangement such that an application program is directly installed in aVM corresponding to the VNF IoT-GW 311 a on the data center 201 side,and by being operated, function of the VNF IoT-GW 311 a can be changed.

Operations after creation of the VNF IoT-GW 311 a are similar to thefirst exemplary embodiment. According to the present exemplaryembodiment, in addition to the effect of the first exemplary embodiment,there is an advantage in that the VNF IoT-GW can be freely created andfunction thereof can be customized. For example, in the first exemplaryembodiment, with physical resource constraint, sharing of IoT-GW isassumed, but in the second exemplary embodiment it is possible forcarrier A and carrier B to respectively start up and use dedicated VNFIoT-GWs. That is, the controller 500 of the present exemplary embodimentfunctions as a control apparatus where a function is built that performsprescribed processing, at an edge node (equivalent to IoT-GW) deployedin a first network, on data transmitted towards a second network(equivalent to data center 201).

In the abovementioned example, a description was given citing an examplein which the VNF IoT-GW 311 a is built using a VNF, but virtualizationis also possible for the GW 321.

THIRD EXEMPLARY EMBODIMENT

Continuing, a detailed description is given concerning a third exemplaryembodiment of the present disclosure, in which a modification is addedto the abovementioned second exemplary embodiment, making reference tothe drawings. FIG. 15 is a diagram for describing a configuration of aVNF IoT-GW in the third exemplary embodiment of the disclosure. A pointof difference from the second exemplary embodiment shown in FIG. 10 isthat function for IoT-GWs represented by reference symbols A to I(reference symbol 3111 a) is realized by VNF, and by modifying chainingthereof, it is possible to add a desired function to a VNF IoT-GW 311 b.For example, by combining function A that performs aggregation of datain a past fixed period, and function B that calculates data average in apast fixed period, it is possible to add these functions to the VNFIoT-GW 311 b.

FIG. 16 is a diagram for describing an example of a configuration methodfor an IoT-GW in a network system in the third exemplary embodiment ofthe present disclosure. For example, carrier A accesses the controller500 from an operator (management terminal) 906 deployed in a virtual NWon a data center 201 side, and transmits a request to add a function tothe VNF IoT-GW 311 b (function implementation request). The controller500 selects a VNF (for example, a VNF corresponding to application A inFIG. 16) corresponding to a request function of carrier A from amongVNFs 902 in FIG. 15, and performs an operation of switching servicechaining. In this way, the request function of carrier A is added to theVNF IoT-GW 311 b.

According to the present exemplary embodiment described above, it ispossible to add a function to the VNF IoT-GW more simply in comparisonwith the second exemplary embodiment. It is to be noted that in thepresent exemplary embodiment also, as shown in FIG. 16, a request tocreate an IoT-GW (function implementation request) or function changerequest may be sent from a business network (on-premises network) ofcarrier A, rather than from the data center 201 side. As shown in FIG.16, with an application program directly installed, a VNF may be createdby requesting the controller 500 to provide a VNF.

FOURTH EXEMPLARY EMBODIMENT

Continuing, a detailed description is given concerning a fourthexemplary embodiment of the present disclosure in which a mobileterminal is used as a data transmission node, making reference to thedrawings. FIG. 17 is a diagram showing a configuration of a networksystem in the fourth exemplary embodiment of the disclosure. A point ofdifferent from the first to third exemplary embodiments shown in FIG. 3etc., is that, instead of an IoT-GW, a GW 321 a and an AP (access point)331 are deployed, and terminals 341 a and 341 b can transmit datareceived from a sensor 600 to a data center 201 side. Since the basicconfiguration and operations are otherwise the same as the firstexemplary embodiment, a description is given below centered on points ofdifference.

The GW 321 a in FIG. 17 is a gateway similar to the GW 321 on the datacenter 201 side. Specifically, the GW 321 a transmits sensor data sentfrom the terminals 341 a and 341 b, to the data center 201 side, via atunnel to the GW 321. And the GW 321 a transmits data sent from the datacenter 201 side, to the terminals 341 a and 341 b, via a tunnel to theGW 321.

The AP 331 is a wireless LAN access point apparatus providing a mobileaccess environment to the terminals 341 a and 341 b.

The terminals 341 a and 341 b are smart phones or mobile terminalapparatuses connected wirelessly or wired to a sensor 600 respectively.After adding prescribed statistical processing to data received from thesensor 600, an application for transmitting to the data center 201 sideis installed in the terminals 341 a and 341 b. Therefore, the terminals341 a and 341 b take on some function of the IoT-GW of the first tothird exemplary embodiments, and by cooperating with the GW 321 a,provide function similar to the IoT-GW.

Similar to the first exemplary embodiment a controller 500 a performsauthentication of new sensors and setting of tunnels according tocarrier, with respect to the GWs 321 and 321 a. On the other hand, inthe present exemplary embodiment it is not necessary for the controller500 a to install an application to realize an IoT-GW to the GW 321.

According to the present exemplary embodiment as described above, it ispossible to transmit sensor data to the data center 201 side via theterminals 341 a and 341 b, as shown in FIG. 18. In the present exemplaryembodiment, by having the GWs 321 and 321 a perform selection of virtualnetwork in accordance with carrier; it is possible to obtain an effectsimilar to the first exemplary embodiment. In addition to the above,according to the present exemplary embodiment, it is possible to use aterminal such as a smartphone as a data transmission node. Accordingly,it is possible to obtain a configuration with few constraints such asinstallation location of data transmission node, wiring, and the like.

According to the present exemplary embodiment, some function of theIoT-GW of the first exemplary embodiment is realized by an applicationoperating on the terminals 341 a and 341 b. Therefore, by carriers A andB installing applications of the terminals 341 a and 341 b, andperforming version upgrading, it is possible to easily customize variousfunctions corresponding to IoT-GW data collection functions orstatistical functions.

In the abovementioned exemplary embodiment a description was given inwhich terminal 341 transmits data to the data center via the GW 321 aand AP 331, but in a case where the terminal 341 has a functionconnecting to a mobile communications network, it is possible to have aconfiguration transmitting sensor data via the mobile communicationsnetwork.

Furthermore, according to the present exemplary embodiment, forterminals 341 a and 341 b it is possible to use a general user terminaldifferent from the carrier. For example, instead of a smart meter ortemperature data monitoring terminal that transmits data measured by anelectrical power meter, it is also possible to entrust transmission ofdata measured by the power meter or thermometer to a general userterminal. In this case, it is possible to give a general user anincentive corresponding with data transmission. For example, in a casewhere a smart meter is out of order, an incentive such as electricalbill discount or granting of points, may be given to a user thatcooperates with data transmission.

Modified Example 1 of Fourth Exemplary Embodiment

Continuing, a description is given concerning a modified example of theabovementioned fourth exemplary embodiment. FIG. 19 is a diagram fordescribing an application installed in terminal 341 a. Referring to FIG.19, two application programs are installed in terminal 341 a. A firstapplication program (IoT GW Application for user A) 3411 a provides afunction to collect data from the sensor 600 a for carrier A, and, onperforming prescribed statistical processing, to transmit to the datacenter 201 side. A second application program (IoT GW Application foruser B) 3411 b provides a function to collect data from the sensor 600 bfor carrier B, and, on performing prescribed statistical processing, totransmit to the data center 201 side. It is to be noted that the 2application programs may have the same function, or may have differentfunction. The frequency at which the application programs gather data orperform statistical processing is determined according to the content ofdata collected from the sensor 600, or the object of service content ofthe carrier using it. In other words, a suitable application program isselected and installed in accordance with sensor type or object of dataprocessing on the data center 201 side, at terminals 341 a and 341 b.From a similar viewpoint in terminal 341 b also, data is collected fromthe sensor 600 a, 600 b of the carrier, and on performing prescribedstatistical processing, an application that transmits to the data center201 side is installed.

As described above, in the fourth exemplary embodiment, it is possibleto install applications for a plurality of carriers, to collect datafrom the sensor 600 (for example, sensors 600 a and 600 b) of differentcarriers respectively, and to transmit to the data center 201 side. Thatis, the plurality of carriers can share terminals used in datatransmission.

Modified Example 2 of Fourth Exemplary Embodiment

Continuing, a description is given concerning another modified exampleof the abovementioned fourth exemplary embodiment. In a case where thereis an account switching function in an application installed in theterminals 341 a and 341 b, it is possible to use the account switchingfunction, and have it used by a plurality of carriers. FIG. 20 is adiagram showing a state where two applications are installed in oneterminal 341, and two accounts can be switched by the respectiveapplications.

Referring to FIG. 20, data of sensor A is collected based on settinginformation of account A of application program X (App X). The collecteddata is transmitted to the GW 321 a after being statistically processedbased on the setting of account A of the application program X (App X).In the GW 321 a, transmission is performed to a virtual NW-A of datacenter S 201S, after a suitable header has been added, based on tunnelinformation set by the controller 500 a. Similarly, the data of sensor Bis collected based on setting information of account B of theapplication program X (App X) of terminal 341, and is transmitted to avirtual NW-B of the data center S 201A. Similarly data of sensor C and Dcollected by application program Y (App Y), after statistical processingby application program Y (App Y), is transmitted to a virtual networkspecified by the data center T.

As described above, in the fourth exemplary embodiment, by installingapplications for a plurality of carriers, and also switching theaccount, it is possible to collect data from a sensor (sensors A to D inFIG. 20) of different respective carriers, and to transmit to the datacenter 201 side. It is to be noted that in the example of FIG. 20, adescription was given in which terminal 341 is made to identify acorrespondence relationship between data from a sensor (sensors A to Din FIG. 20) and application setting, by using the account switchingfunction of an application, but it is possible to use other methodsalso. For example, in a case where the OS (operating system) of terminal341 is an OS handling multiple users, by respective carriers logging inas different users and performing setting in applications, a similarmulti-user environment is realized.

As described above, in a case where a plurality of carriers shareterminal 341, it is preferable to limit entities that can install anapplication or change the setting of an application. For example, byusing a user authentication function of terminal 341 itself or anapplication for authentication installed in terminal 341, it is possibleto determine whether an operator of terminal 341 has appropriateauthority.

FIFTH EXEMPLARY EMBODIMENT

Continuing, a description is given of a fifth exemplary embodiment ofthe present disclosure combining the first to fourth exemplaryembodiments described above. FIG. 21 is a diagram showing aconfiguration of a network system in the fifth exemplary embodiment ofthe disclosure.

Referring to FIG. 21, a first network 101 a, an EPC (Evolved PacketCore) network, a public wireless network, a controller 500 b, and datacenters 201S and 201T are connected via a third network 401. Thecontroller 500 b controls a GW 321 or a IoT-GW 311 that function as edgenodes of these networks, to build virtual network functions for eachrespective carrier.

Therefore, the first network 101 a and the data center 201S (data center201T) of FIG. 21 correspond to the configuration of the first exemplaryembodiment. The IoT-GW 311 of the first network 101 a of FIG. 21 can beconfigured by a VNF, similarly to the second and third exemplaryembodiments.

For terminal 341 of FIG. 21, the configuration for transmitting data ofsensors 600 b and 600 c to the data center 201S (data center 201T), viathe EPC (Evolved Packet Core) network or the public wireless network,correspond to the configuration of the fourth exemplary embodiment.

In the example of FIG. 21, the data center 201S and the data center 201Tare connected to a main data center (main DC) 201U. In this type of maindata center (main DC) 201U, data sent from various sensors is analyzed,and it is possible to provide a big data analysis function providingvarious types of forecast and service.

As described above, the first to fourth exemplary embodiments of thepresent disclosure can be combined consistently.

A description has been given above of respective exemplary embodimentsof the present invention, but the present invention is not limited tothe abovementioned exemplary embodiments, and further modifications,substitutions and adjustments may be added within a scope that does notdepart from fundamental technical concepts of the invention. Forexample, network configurations, respective element configurations andmessage expression forms shown in the respective drawings are examplesfor the purpose of aiding understanding of the invention, and are notintended to limit the invention to configurations illustrated in thedrawings.

For example, in the abovementioned various exemplary embodiments,descriptions were given of building virtual network function between theIoT-GW 311 and the GW 321 using a tunneling protocol, but methods ofconfiguring virtual network function are not limited to this method. Forexample, for the controller 500, it is possible to use a method ofdeploying a centralized controller known as an OpenFlow controller or anSDN (Software Defined Network) controller. In this case, for thecentralized controllers it is possible to use a method of configuringanother virtual network in which physical nodes in the third network 401operate as virtual nodes, and the third network is logically separated.

In the abovementioned respective exemplary embodiments descriptions weregiven in which virtual networks are provided for each carrier, but evenwith the same carrier, in a case of providing different services, casesmay be assumed where it is better to separate the virtual networks. Inthis case, the virtual networks are built for each service.

Finally, preferred modes of the present invention are summarized.

[First Mode]

(Refer to the network system according to the first aspect describedabove.)

[Second Mode]

It is preferred that the virtual network and the first physical networkbe connected to a first edge node provided on a boundary between thefirst physical network and an external network in the network system.

[Third Mode]

It is preferred that the virtual network and the second physical networkbe connected to a second edge node provided on a boundary between thesecond physical network and an external network in the network system.

[Fourth Mode]

It is preferred that the first and the second edge nodes be gatewaysthat configure a tunnel for each of the services with an opposite edgenode to transmit/receive data in the network system.

[Fifth Mode]

It is preferred that the network system further comprise a controlapparatus that controls each virtual network configured for each of theservices and controls the first and the second edge nodes.

[Sixth Mode]

It is preferred that, when a sensor used for any of the services isadded to the first physical network in network system, the first edgenode ask the control apparatus whether or not data transmitted by thesensor can be transmitted to the second physical network.

[Seventh Mode]

(Refer to the control apparatus according to the second aspect describedabove.)

[Eighth Mode]

(Refer to the method for constructing a virtual network according to thethird aspect described above.)

[Ninth Mode]

(Refer to the program according to the fourth aspect described above.)It is to be noted that the abovementioned seventh to ninth modes may beexpanded with regard to the second to sixth modes, similar to the firstmode.

It is to be noted that the various disclosures of the abovementionedPatent Literature and Non-Patent Literature are incorporated herein byreference thereto. Modifications and adjustments of exemplaryembodiments and examples may be made within the bounds of the entiredisclosure (including the scope of the claims) of the present invention,and also based on fundamental technological concepts thereof. Variouscombinations and selections (including partial deletion) of variousdisclosed elements (including respective elements of the respectiveclaims, respective elements of the respective exemplary embodiments andexamples, respective elements of the respective drawings and the like)are possible within the scope of the disclosure of the presentinvention. That is, the present invention clearly includes every type oftransformation and modification that a person skilled in the art canrealize according to the entire disclosure including the scope of theclaims and to technological concepts thereof. In particular, with regardto numerical ranges described in the present specification, arbitrarynumerical values and small ranges included in the relevant ranges shouldbe interpreted to be specifically described even where there is noparticular description thereof.

REFERENCE SIGNS LIST

-   100: first physical network-   101: physical network-   101 a: first network-   200: second physical network-   201, 201S, 201T: data center-   201U: main data center-   310-320: edge node-   311: IoT-GW-   311 a, 311 b: VNF IoT-GW-   321, 321 a, 321S, 321T: GW-   331: access point-   341, 341 a, 341 b: terminal-   400: network system-   401: third network-   500, 500 a, 500 b: controller-   501: authentication information storage part-   502: virtual network setting storage part-   503: authentication part-   504: virtual network control part-   600, 600 a to 600 c: sensor-   901: NFVI-   902: VNF-   903: VM management part-   904: NW management part-   905: orchestrator-   906: operator-   930: controller-   3111 a: VNF-   3411 a, 3411 b: application

1. A network system comprising: a first sensor operated by a first carrier; a second sensor operated by a second carrier; a first gateway configured to receive data from the first sensor and the second sensor; and a data center; wherein the data center comprising: a first virtual network configured to provide a first service by the first carrier; a second virtual network configured to provide a second service by the second carrier; and a second gateway configured to forward the received data to the first virtual network or the second virtual network, based on source of the received data.
 2. The network system according to claim 1, wherein the second gateway configured to forward the received data to the first virtual network, when the received data is sent from the first sensor, and wherein the second gateway configured to forward the received data to the second virtual network, when the received data is sent from the second sensor.
 3. The network system according to claim 1, wherein the first gateway configured to establish tunnel between the second gateway, for each of the first service and the second service.
 4. The network system according to claim 1, wherein the second gateway configured to establish tunnel between the first gateway, for each of the first service and the second service.
 5. The network system according to claim 1, further comprising a control apparatus configured to control the first virtual network, the second virtual network, the first gateway and the second gateway.
 6. A data center connected to a first sensor operated by a first carrier, a second sensor operated by a second carrier and a first gateway configured to receive data from the first sensor and the second sensor, the data center comprising; a first virtual network configured to provide a first service by the first carrier; a second virtual network configured to provide a second service by the second carrier; and a second gateway configured to forward the received data to the first virtual network or the second virtual network, based on source of the received data.
 7. The data center according to claim 6, wherein the second gateway configured to forward the received data to the first virtual network, when the received data is sent from the first sensor, and wherein the second gateway configured to forward the received data to the second virtual network, when the received data is sent from the second sensor.
 8. The data center according to claim 6, wherein the first gateway configured to establish a tunnel to the second gateway, for each of the first service and the second service.
 9. The data center according to claim 6, wherein the second gateway configured to establish a tunnel to the first gateway, for each of the first service and the second service.
 10. The data center according to claim 6, further comprising a control apparatus configured to control the first virtual network, the second virtual network, the first gateway and the second gateway.
 11. A communication method comprising: receiving data from a first sensor operated by a first carrier and/or a second sensor operated by a second carrier; and forwarding the received data to a first virtual network or a second virtual network, based on source of the received data, wherein the first virtual network configured to provide a first service by the first carrier, and wherein the second virtual network configured to provide a second service by the second carrier.
 12. The communication method according to claim 11, wherein the received data is forwarded to the first virtual network by a second gateway, when the received data is sent from the first sensor, and wherein the received data is forwarded to the second virtual network by the second gateway, when the received data is sent from the second sensor.
 13. The communication method according to claim 11, wherein a tunnel to the second gateway is established by a first gateway, for each of the first service and the second service.
 14. The communication method according to claim 11, wherein a tunnel to the first gateway is established by the second gateway, for each of the first service and the second service. 